Multi-user remote health monitoring system with biometrics support

ABSTRACT

The invention presents a networked system for identifying an individual, communicating information to the individual, and remotely monitoring the individual. The system includes a remotely programmable apparatus that occasionally connects to a server via a communication network such as the Internet. The remotely programmable apparatus interacts with the individual in accordance with a script program received from the server Among other capabilities, the script program may instruct the remotely programmable apparatus to identify the individual, to communicate information to the individual, to communicate queries to the individual, to receive responses to the queries, and to transmit information identifying the individual and the responses from the remotely programmable apparatus to the server. Information identifying the individual may be obtained via a biometrics sensor, a data card, a remote monitoring device, or the interception of data from a separate information system. The information identifying the individual may be used by either or both the server system and remotely programmable apparatus for security, customization and other purposes. As the present invention has multi-user capabilities, it can be used in a public place, such as a pharmacy or health care clinic. The multi-user capabilities also allow collection and tracking of user data for the healthcare industry.

CLAIM FOR PRIORITY

[0001] This application is a Continuation-in-Part of U.S. Ser. No. 09/665,442 filed Sep. 19, 2000, which is a Continuation-in-Part of U.S. Ser. No. 09/357,536 filed Jul. 19, 1999, which is a Continuation of U.S. Pat. No. 5,940,801 issued on Aug. 17, 1999, which is a Continuation of U.S. Pat. No. 5,828,943 issued Oct. 27, 1998, which is a Continuation of U.S. Ser. No. 08/682,385 filed Jul. 17, 1996, now abandoned, which is a Continuation of U.S. Ser. No. 08/479,570 filed Jun. 7, 1995, now abandoned, which is a Continuation of U.S. Ser. No. 08/233,674 filed Apr. 26, 1994, now abandoned.

[0002] This application is also a Continuation-in-Part of U.S. Ser. No. 09/293,363 filed on Apr. 16, 1999, U.S. Ser. No. 09/203,882 filed on Dec. 1, 1998, U.S. Ser. No. 09/159,219 filed on Sep. 23, 1998, U.S. Ser. No. 09/159,058 filed on Sep. 23, 1998, U.S. Ser. No. 09/203,880 filed Dec. 1, 1998, U.S. Ser. No. 09/201,323 filed on Nov. 30, 1998, U.S. Ser. No. 09/320,004 filed on May 26, 1999, U.S. Ser. No. 09/318,708 filed on May 26, 1999, and U.S. Ser. No. 09/274,433 filed on Mar. 22, 1999 now abandoned.

[0003] This application is a Continuation-in-Part of a U.S. Ser. No. 09/422,046 filed Oct. 20, 1999, which is a continuation of U.S. Pat. No. 6,168,563 issued on Jan. 2, 2001, which is a Continuation of U.S. Pat. No. 5,899,855 issued on May 4, 1999, which is a Continuation of U.S. Ser. No. 08/233,397 filed on Apr. 26, 1994 now abandoned, which is a Continuation-in-Part of U.S. Pat. No. 5,307,263 issued on Apr. 26, 1994, and also U.S. Ser. No. 09/422,046 is a Continuation-in-Part of U.S. Pat. No. 5,997,476 issued on Dec. 7, 1999, which is a Continuation-in-Part of U.S. Pat. No. 5,897,493 issued on Apr. 27, 1999, which claims priority to Provisional Application Serial No. 60/041,746 filed on Mar. 28, 1997 and Provisional Application Serial No. 60/041,751 filed on Mar. 28, 1997.

[0004] This application is a Continuation-in-Part of U.S. Ser. No. 09/237,194 filed on Jan. 26, 1999, which is a Continuation of U.S. Pat. No. 5,899,855 issued on May 4, 1999, which is a Continuation of U.S. Ser. No. 08/233,397 filed on Apr. 26, 1994 now abandoned, which is a Continuation-in-Part of U.S. Pat. No. 5,307,263 issued Apr. 26, 1994.

[0005] This application is a Continuation-in-Part of U.S. Ser. No. 09/201,372 filed on Nov. 30, 1998, which is a Continuation-in-Part of U.S. Pat. No. 5,879,163 issued on Mar. 9, 1999.

[0006] This application is a Continuation-in-Part of U.S. Ser. No. 09/378,188 filed on Aug. 20, 1999, which is a Continuation of U.S. Pat. No. 5,985,559 issued on Nov. 16, 1999, which is a Continuation-in-Part of U.S. Pat. No. 5,897,493 issued Apr. 27, 1999.

[0007] This application is a Continuation-in-Part of U.S. Ser. No. 09/304,447 filed May 3, 1999, which is a Continuation of U.S. Pat. No. 5,933,136 issued Aug. 3, 1999.

[0008] This application is a Continuation-in-Part of U.S. Ser. No. 09/531,237 filed Mar. 21, 2000, which is a Continuation-in-Part of U.S. Pat. No. 6,368,273 issued Apr. 19, 2002, which is a Divisional of U.S. Pat. No. 5,997,476 issued on Dec. 7, 1999, which is a Continuation-in-Part of U.S. Pat. No. 5,897,493 issued Apr. 27, 1999, which claims priority to Provisional Application Serial No. 60/041,746 filed Mar. 28, 1997, and also Provisional Application Serial No. 60/041,751 filed Mar. 28, 1997 filed Mar. 28, 1997.

[0009] This application is a Continuation-in-Part of U.S. Ser. No. 09/540,482 filed Mar. 31, 2000, which is a Continuation of U.S. Ser. No. 09/394,219 filed Sep. 13, 1999, which is a Continuation of U.S. Pat. No. 5,951,300 issued Sep. 14, 1999.

[0010] This application is a Continuation-in-Part of U.S. Ser. No. 09/518,426 filed Mar. 3, 2000 now abandoned, which is a Continuation of U.S. Pat. No. 6,068,615 issued May 30, 2000, which is a Continuation-in-Part of U.S. Pat. No. 5,782,814 issued Jul. 21, 1998, which is a Continuation-in-Part of U.S. Pat. No. 5,569,212 issued Oct. 29, 1996.

[0011] This application is a Continuation-in-Part of U.S. Ser. No. 09/495,809 filed Feb. 1, 2000, which is a Continuation-in-Part of U.S. Pat. No. 6,186,145 issued Feb. 13, 2001, which is a Continuation-in-Part of U.S. Pat. No. 5,913,310 issued Jun. 22, 1999, which is a Continuation-in-Part of U.S. Pat. No. 5,918,603 issued Jul. 6, 1999, which is a Continuation of U.S. Pat. No. 5,678,571 issued Oct. 21, 1997, U.S. Ser. No. 09/495,809 is also a Continuation of U.S. Pat. No. 6,334,778 issued on Jan. 1, 2002, which is a Continuation-in-Part of U.S. Pat. No. 5,997,476 issued Dec. 7, 1999, which is a Continuation-in-Part of U.S. Pat. No. 5,897,493 issued Apr. 27, 1999, which claims priority to Provisional Application Serial No. 60/041,746 filed Mar. 28, 1997 and to Provisional Application Serial No. 60/041,751 filed Mar. 28, 1997, and also U.S. Pat. No. 6,334,778 is a Continuation-in-Part of U.S. Pat. No. 5,940,801 issued Aug. 17, 1999, which is a Continuation of U.S. Pat. No. 5,828,943 issued Oct. 27, 1998, which is a Continuation of U.S. Ser. No. 08/682,385 filed Jul. 17, 1996 now abandoned, which is a Continuation of U.S. Ser. No. 08/479,570 filed Jun. 7, 1995 now abandoned, which is a Continuation of U.S. Ser. No. 08/233,674 filed Apr. 26, 1994 now abandoned.

[0012] This application is a Continuation-in-Part of U.S. Ser. No. 09/496,893 filed Feb. 2, 2000, which is a Continuation of U.S. Ser. No. 09/041,809 filed Mar. 13, 1998 now abandoned.

[0013] This application is a Continuation-in-Part of U.S. Ser. No. 09/658,209 filed Sep. 8, 2000, which is a Continuation-in-Part of U.S. Ser. No. 09/237,194 filed Jan. 1, 1999, which is a Continuation of U.S. Pat. No. 5,899,855 issued May 4, 1999, which is a Continuation of U.S. Ser. No. 08/233,397 filed Apr. 26, 1994 now abandoned, which is a Continuation-in-Part of U.S. Pat. No. 5,307,263 issued Apr. 16, 1994.

[0014] This application is a Continuation-in-Part of U.S. Pat. No. 6,240,393 issued on May 29, 2001, which is a Continuation-in-Part of U.S. Pat. No. 6,023,686 issued Feb. 8, 2000, which is a Continuation-in-Part of U.S. Pat. No. 5,887,133 issued on Mar. 23, 1999, and which is a Continuation-in-Part of U.S. Pat. No. 5,794,219 issued on Aug. 11, 1998.

[0015] This application is a Continuation-in-Part of U.S. Ser. No. 09/152,353 filed Sep. 14, 1998, which is a Continuation-in-Part of U.S. Pat. No. 5,832,448 issued Nov. 3, 1998.

[0016] This application is a Continuation-in-Part of U.S. Pat. No. 6,167,386 issued Dec. 26, 2000, which is a Continuation of U.S. Pat. No. 6,023,686 issued Feb. 8, 2000, which is a Continuation-in-Part of U.S. Pat. No. 5,794,219 issued Aug. 11, 1998, and a Continuation-in-Part of U.S. Pat. No. 5,887,133 issued Mar. 23, 1999.

[0017] This application is a Continuation-in-Part of U.S. Ser. No. 09/441,408 filed Nov. 16, 1999 now abandoned, and application U.S. Ser. No. 09/810,334 filed Mar. 14, 2001, which claims priority to Provisional Application Serial No. 60/189,536 filed on Mar. 15, 2000.

[0018] This application is a Continuation-in-Part of U.S. Ser. No. 09/810,865 filed Mar. 16, 2001, which is a Continuation of U.S. Pat. No. 6,233,539 issued May 15, 2001, which is a Continuation of U.S. Pat. No. 5,956,501 issued Sep. 21, 1999.

[0019] This application is a Continuation-in-Part of U.S. Ser. No. 10/024,445 filed Dec. 17, 2001, which claims priority to Provisional Application No. 60/256,715 filed Dec. 18, 2000.

[0020] This application is a Continuation-in-Part of U.S. Ser. No. 09/274,431 filed Mar. 22, 1999, and U.S. Pat. No. 6,330,426 issued Dec. 11, 2001, which is a Continuation-in-Part of U.S. Ser. No. 08/953,883 filed Oct. 20, 1997 now abandoned, which is a Continuation-in-Part of U.S. Pat. No. 6,144,837 issued Nov. 7, 2000, which is a Continuation of U.S. Pat. No. 5,601,435 issued Feb. 11, 1997. U.S. Pat. No. 6,330,426 is also a Continuation of U.S. Pat. No. 5,913,310 issued Jun. 22, 1999, which is a Continuation-in-Part of U.S. Pat. No. 5,918,603 issued Jul. 6, 1999, which is a Continuation of U.S. Pat. No. 5,678,571 issued Oct. 21, 1997.

[0021] This application is a Continuation-in-Part of U.S. Pat. No. 6,210,272 issued Apr. 3, 1997.

[0022] This application claims priority from U.S. Provisional Application No. 60/239,533 filed Oct. 10, 2000, and U.S. Provisional Application No. 60/242,681 filed Oct. 20, 2000 now abandoned.

[0023] This application claims priority from U.S. Provisional Application No. 60/336,198 filed Oct. 23, 2001.

[0024] This application claims priority from U.S. Provisional Application No. 60/326,521 filed Oct. 1, 2001.

[0025] This application claims priority from U.S. Provisional Application No. 60/316,804 filed Aug. 31, 2001.

[0026] All of the above named applications are incorporated by reference.

FIELD OF THE INVENTION

[0027] This invention relates generally to remote health monitoring systems. In particular, it relates to a multi-user remote health monitoring system which is capable of identifying a particular user in a number of different ways. The multi-user remote health monitoring system can also be used for tracking and collecting patient data.

BACKGROUND OF THE INVENTION

[0028] In the United States alone, over 100 million people have chronic health conditions, accounting for an estimated $700 billion in annual medical costs. In an effort to control these medical costs, many healthcare providers have initiated outpatient or home healthcare programs for their patients. The potential benefits of these programs are particularly great for chronically ill patients who must treat their diseases on a daily basis. However, the success of these programs is dependent upon the ability of the healthcare providers to monitor the patients remotely to avert medical problems before they become complicated and costly. Unfortunately, no convenient and cost effective monitoring system exists for the patients who have the greatest need for monitoring, namely the poor and the elderly.

[0029] Prior attempts to monitor patients remotely have included the use of personal computers and modems to establish communication between patients and healthcare providers. However, computers are too expensive to give away and the patients who already own computers are only a fraction of the total population. Further, the patients who own computers are typically young, well educated, and have good healthcare coverage. Thus, these patients do not have the greatest unmet medical needs. The patients who have the greatest unmet medical needs are the poor and elderly who do not own computers or who are unfamiliar with their use.

[0030] Similar attempts to establish communication between patients and healthcare providers have included the use of the Internet and internet terminals. Although internet terminals are somewhat less costly than personal computers, they are still too expensive to give away to patients. Moreover, monthly on-line access charges are prohibitive.

[0031] Other attempts to monitor patients remotely have included the use of medical monitoring devices with built-in modems. Examples of such monitoring devices include blood glucose meters, respiratory flow meters, and heart rate monitors. Unfortunately, these monitoring devices are only designed to collect physiological data from the patients. They do not allow flexible and dynamic querying of the patients for other information, such as quality of life measures or psycho-social variables of illness. Another problem with such devices is that only the most self-motivated patients generate enough useful physiological data and call in regularly. Thus this method is not a good way to reach non-compliant patients.

[0032] Prior attempts to monitor patients remotely have also included the use of interactive telephone or video response systems. Such interactive systems are disclosed in U.S. Pat. No. 5,390,238 issued to Kirk et al. on Feb. 14, 1995, U.S. Pat. No. 5,434,611 issued to Tamura on Jul. 18, 1995, and U.S. Pat. No. 5,441,047 issued to David et al. on Aug. 15, 1995. One disadvantage of these systems is that they either require a patient to call in to a central facility to be monitored or require the central facility to call the patient according to a rigid monitoring schedule.

[0033] If the patients are required to call the central facility, only the compliant patients will actually call regularly to be monitored. Non-compliant patients will typically wait until an emergency situation develops before contacting their healthcare provider, thus defeating the purpose of the monitoring system. If the central facility calls each patient according to a monitoring schedule, it is intrusive to the patient's life and resistance to the monitoring grows over time.

[0034] Interactive telephone response systems, moreover, are generally incapable of collecting medical data from monitoring devices, such as blood glucose meters, respiratory flow meters, or heart rate monitors. In addition, patients tend to dislike the regular intrusion which decreases their compliance with the monitoring system.

[0035] Interactive video systems, on the other hand, cost around $20,000 for installation and are prohibitively expensive for the majority of patients. It is also difficult to identify each patient uniquely using this system.

[0036] A further disadvantage of these conventional interactive response systems is that they are aimed at a single user, thus preventing any multi-user capabilities. Interactive video response systems are too expensive to install for a single user. Interactive telephone response systems can be used for more than one member of a household, but it is often difficult to distinguish between the different patients. These characteristics, in conjunction with the fact that patients using the conventional interactive response systems do not usually exhibit regular use patterns, means that the patient data collected is statistically unreliable. Thus, these systems are not equipped to handle patient data collection and tracking.

[0037] Also, as conventional interactive response systems are intended for use in a patient's home, they are not suited for use in public areas. Their single user nature makes them ill-equipped to handle a large volume of users. Touch screen kiosks, which are commonly used in lobbies of public buildings to disseminate information, are difficult to individualize for a patient and are also very expensive. In addition, kiosks are self-contained and not designed to work with other separate information systems, such as the Internet or a healthcare provider's information system.

OBJECTS AND ADVANTAGES OF THE INVENTION

[0038] In view of the above, it is an object of the present invention to provide a simple and inexpensive system for identifying and remotely monitoring a plurality of patients. It is another object of the present invention to provide a remote monitoring system which incurs a minimal hardware cost per patient. It is another object of the present invention to communicate information to a plurality of patients. It is another object of the invention to provide a system which allows flexible and dynamic querying of a plurality of patients. Another object of the present invention is to allow automatic identification of an individual by use of biometric information, a data card, a remote monitoring device, or a separate information system. It is another object of the present invention to assign scripts to patients automatically. It is a further object of the present invention to allow the collection and tracking of data from a plurality of patients for statistical analysis. It is another object of the present invention to provide an interactive response system which accepts and uses input from separate information systems. A final object of the present invention is to provide individualized patient interaction at a public terminal without increasing administration costs.

[0039] These and other objects and advantages will become more apparent after consideration of the ensuing description and the accompanying drawings.

SUMMARY

[0040] The invention presents a networked system for remotely identifying and monitoring a plurality of individuals, and for communicating information to the individuals. The system includes a server, and a workstation for entering into the server query sets to be answered by the individuals. The server is preferably a world wide web server and the workstation is preferably a personal computer or network terminal connected to the web server via the Internet. The system also includes a remotely programmable apparatus for identifying and interacting with the individuals. The remotely programmable apparatus is connected to the server via a communication network, preferably the Internet. The remotely programmable apparatus interacts with the individuals in accordance with script programs received from the server.

[0041] The server includes a script generator for generating script programs from the query sets which are entered through the workstation. The script programs are executable by the remotely programmable apparatus to communicate the query sets to the individuals, to receive responses to the query sets, and to transmit the responses from the remotely programmable apparatus to the server. The server also includes a database connected to the script generator for storing the script program and the responses to the queries. The database also stores a list of individuals or individual types, and for each individual or individual type, has a pointer to at least one script program. The server also has script assignment means connected to the database, which assigns to an individual at least one script program, according to script assignment information. The workstation allows a healthcare provider to enter in the script assignment information or the script programs may be automatically assigned based on individual identification information gathered from a input through an interface to the remote apparatus, a biometric sensor, a data card, a remote monitoring device, or other separate information system.

[0042] The remotely programmable apparatus has a communication device, such as a modem, for receiving the script programs from the server and for transmitting the responses to the server. The remotely programmable apparatus also has a user interface for communicating the query sets to the individuals and for receiving the responses to the query sets. In the preferred embodiment, the user interface includes a display for displaying the query sets and user input buttons for entering the responses to the query sets. In an alternative embodiment, the user interface includes a speech synthesizer for audibly communicating the query sets and a speech recognizer for receiving spoken responses to the query sets.

[0043] The remotely programmable apparatus also includes a memory for storing the script programs and the responses to the query sets. The remotely programmable apparatus further includes a microprocessor connected to the communication device, the user interface, and the memory. The microprocessor executes the script programs to identify the individual, communicate the query sets to the individual, receive the responses to the query sets, and transmit the responses to the server through the communication network.

[0044] In one embodiment, the system also includes at least one monitoring device for producing measurements of a physiological condition of the individual and for transmitting the measurements to the apparatus. The monitoring device can also be used to help the remotely programmable apparatus identify the individual. The remotely programmable apparatus includes a device interface connected to the microprocessor for receiving the measurements from the monitoring device. The measurements are stored in the memory and transmitted to the server along with the individual's identity and the responses to the query sets. The server also preferably includes a report generator connected to the database for generating a report of the measurements and responses. The report is displayed on the workstation.

[0045] As the present invention has multi-user capabilities, it must identify each individual or individual type in order to select the correct script program. In one embodiment, the individual can enter his or her unique identification code into the remotely programmable apparatus. The code is sent to the server and used to determine which script program to send back to the apparatus.

[0046] In another embodiment, the system uses a data card, which contains information about an individual's identity. The remotely programmable apparatus includes a data card reader in which the data card can be placed and read. A personal identification number (PIN) can also be used in conjunction with the data card in order confirm an individual's identity. In this embodiment, the present invention resembles an ATM machine.

[0047] In yet another embodiment, the system utilizes a biometric information gathered using a biometric sensor to determine an individual's identity. The biometric information is used by the methods and systems of the invention to assign script programs, to customize script programs for the identified individual and to provide security against unauthorized use for either or both the remote apparatus and server systems. Examples of biometric information useable by the invention include: retina metrics, iris metrics, voice print metrics, body measurement metrics, handwriting metrics, body odor metrics, heart beat signature metrics and biometrics that may be discernable from the individual's body fluids such as blood, urine or breath.

[0048] The system of the present invention can also identify an individual or individual type (e.g., diabetic) by intercepting data from a separate information system. Data sent from a server of the separate information system to a printer can pass through the remotely programmable apparatus, which can identify the individual and send the data to the server of the present invention. The data passing through the remotely programmable apparatus can also trigger a script program, which can display queries for the individual to answer, or send information to the printer to be printed. An example of this embodiment has the remotely programmable apparatus located in series between a pharmacy server and a pharmacy printer.

[0049] Finally, the multi-user characteristic of the present invention makes it possible to collect and track data on individuals. The information generated can be used in a number of ways—for demographic marketing reports for pharmaceutical companies or for epidemiological studies by health care providers.

BRIEF DESCRIPTION OF THE DRAWINGS

[0050]FIG. 1 is a block diagram of a networked system according to a preferred embodiment of the invention.

[0051]FIG. 2 is a block diagram illustrating the interaction of the components of the system of FIG. 1.

[0052]FIG. 3 is a perspective view of a remotely programmable apparatus of the system of FIG. 1.

[0053]FIG. 4 is a block diagram illustrating the components of the apparatus of FIG. 3.

[0054]FIG. 5 is a script entry screen according to the preferred embodiment of the invention.

[0055]FIG. 6A is a listing of a sample script program according to the preferred embodiment of the invention.

[0056]FIG. 6B is a continuation of the listing of FIG. 6A.

[0057]FIG. 7 is a script assignment screen according to the preferred embodiment of the invention.

[0058]FIG. 8 is a sample prompt appearing on a display of the apparatus of FIG. 3.

[0059]FIG. 9 is a sample query displayed on a workstation of the system of FIG. 3.

[0060]FIG. 10 is a sample patient report displayed on the workstation of the system of FIG. 1.

[0061]FIG. 11A is a flow chart illustrating the steps included in a monitoring application executed by the server of FIG. 1 according to the preferred embodiment of the invention.

[0062] FIGS. 11B-C are a continuation of the flow chart of FIG. 11A.

[0063]FIG. 12A is a flow chart illustrating the steps included in the script program of FIGS. 6A-6B.

[0064] FIGS. 12B-C are a continuation of the flow chart of FIG. 12A.

[0065]FIG. 13 flow chart illustrating the steps included in a monitoring application executed by the server of FIG. 1 according to an alternative embodiment of the invention.

[0066]FIG. 14A is a flow chart illustrating the steps included in the script program used in the alternative embodiment of the invention.

[0067]FIG. 14B is a continuation of the flow chart of FIG. 14A.

[0068]FIG. 15 is a perspective view of a remotely programmable apparatus according to a second embodiment of the invention.

[0069]FIG. 16 is a sample prompt appearing on a display of the apparatus of FIG. 15.

[0070]FIG. 17 is a block diagram illustrating the components of the apparatus of FIG. 15.

[0071]FIG. 18 is a schematic block diagram illustrating the interaction of the server of FIG. 1 with the apparatus of FIG. 3 according to a third embodiment of the invention.

[0072]FIG. 19 is a first sample message, appearing on the display of the apparatus of FIG. 3.

[0073]FIG. 20 is a second sample message, appearing on the display of the apparatus of FIG. 3.

[0074]FIG. 21 is a script entry screen according to the third embodiment of the invention.

[0075]FIG. 22 is a block diagram of a networked system according to the data interception embodiment of the invention.

[0076]FIG. 23 is a perspective view of a remotely programmable apparatus of the system of FIG. 22.

[0077]FIG. 24 is a block diagram illustrating the components of the apparatus of FIG. 23.

DETAILED DESCRIPTION

[0078] The invention presents a system and method for remotely identifying and monitoring individuals, and for communicating information to the individuals. In a preferred embodiment of the invention, the individuals are patients and the system is used to collect data relating to the health status of the patients. The data can be used by healthcare providers or pharmaceutical companies for research or marketing purposes.

[0079] In the present invention, an individual is designated to mean a unique patient or a unique patient type, such as a diabetic. Also, it is to be understood that the invention is not limited to remote patient monitoring. The system and method of the invention may be used for any type of remote monitoring application. The invention may also be implemented as an automated messaging system for communicating information to individuals, as will be discussed in an alternative embodiment below.

[0080] A preferred embodiment of the invention is illustrated in FIGS. 1-12. Referring to FIG. 1, a networked system 16 includes a server 18 and a workstation 20 connected to server 18 through a communication network 24. Server 18 is preferably a world wide web server and communication network 24 is preferably the Internet. It will be apparent to one skilled in the art that server 18 may comprise a single stand-alone computer or multiple computers distributed throughout a network. Workstation 20 is preferably a personal computer, remote terminal, or web TV unit connected to server 18 via the Internet. Workstation 20 functions as a workstation for entering in server 18 messages and queries to be communicated to the patients.

[0081] System 16 also includes a remotely programmable apparatus 26 for monitoring patients. Apparatus 26 is designed to interact with a plurality of patients in accordance with script programs received from server 18. Apparatus 26 is in communication with server 18 through communication network 24, preferably the Internet. Alternatively, apparatus 26 may be placed in communication with server 18 via wireless communication networks, cellular networks, telephone networks, or any other network which allows apparatus 26 to exchange data with server 18. For clarity of illustration, only one apparatus 26 is shown in FIG. 1. It is to be understood that system 16 may include any number of apparatuses, with each apparatus used to monitor any number of patients.

[0082] In the preferred embodiment, each patient to be monitored is also provided with a monitoring device 28. Monitoring device 28 is designed to produce measurements of a physiological condition of the patient, record the measurements, and transmit the measurements to apparatus 26 through a standard connection cable 30. Examples of suitable monitoring devices 28 include blood glucose meters, respiratory flow meters, blood pressure cuffs, electronic weight scales, and pulse rate monitors. Such monitoring devices are well known in the art. The specific type of monitoring device provided to each patient is dependent upon the patient's disease. For example, diabetes patients are provided with a blood glucose meters for measuring blood glucose concentrations, asthma patients are provided with respiratory flow meters for measuring peak flow rates, obesity patients are provided with weight scales, etc.

[0083]FIG. 2 shows server 18, workstation 20, and apparatus 26 in greater detail. Server 18 includes a database 38 for storing script programs 40. Script programs 40 are executed by apparatus 26 to communicate queries and messages to a patient, receive responses 42 to the queries, collect monitoring device measurements 44, and transmit responses 42 and measurements 44 to server 18. Database 38 is designed to store responses 42 and measurements 44. Database 38 further includes a look-up table 46. Table 46 contains a list of the patients and patient types to be monitored, and for each patient or patient type, a unique patient identification code and a respective pointer to the script program assigned to the patient. Each apparatus 26 is designed to execute assigned script programs 40 which it receives from server 18. As each apparatus 26 is used by a number of patients, apparatus 26 can execute any number of script programs 40.

[0084] FIGS. 3-4 show the structure of each apparatus 26 according to the preferred embodiment. Referring to FIG. 3, apparatus 26 includes a housing 62. Housing 62 is sufficiently compact to enable apparatus 26 to be placed unobtrusively on a pharmacy counter or check stand counter. Apparatus 26 also includes a display 64 for displaying queries and prompts to the patient. In the preferred embodiment, display 64 is a liquid crystal display (LCD).

[0085] Four user input buttons 70A, 70B, 70C, and 70D are located adjacent display 64. User input buttons 70A, 70B, 70C, and 70D are for entering in apparatus 26 responses to the queries and prompts. In the preferred embodiment, user input buttons 70A, 70B, 70C, and 70D are momentary contact push buttons. In alternative embodiments, user input buttons 70A, 70B, 70C, and 70D may be replaced by switches, keys, a touch sensitive display screen, or any other data input device.

[0086] Three monitoring device jacks 68A, 68B, and 68C are located on a surface of housing 62. Device jacks 68A, 68B, and 68C are for connecting apparatus 26 to a number of monitoring devices 28, such as blood glucose meters, respiratory flow meters, or blood pressure cuffs, through respective connection cables (not shown). Apparatus 26 also includes a modem jack 66 for connecting apparatus 26 to a telephone jack through a standard connection cord (not shown). Apparatus 26 further includes a visual indicator, such as a light emitting diode (LED) 74. LED 74 is for visually notifying the patient that he or she has unanswered queries stored in apparatus 26.

[0087] Apparatus 26 also contains a data card reader 63. Data card reader 63 is capable of reading a data card 65 containing information about a patient. In the present invention, data card 65 contains the patient's identity, condition or disease, and possibly prescription information. Data card 65 is placed in data card reader 63, thus allowing apparatus 26 to identify the patient and assign script program 40. Apparatus 26 also has a printer port 67, allowing apparatus 26 to be directly connected to a printer. Queries 94, responses 42, device measurements 44, and other pertinent information stored on apparatus 26 can be printed directly.

[0088] The apparatus also includes a biometric sensor 71 for gathering biometric information from the user. Examples of biometric sensors that may be used by the appratus 26 include an optical device (e.g., a camera created from a CCD), a silicon sensor (e.g., a chip that gathers information using the capacitance occurring as a result of a body part coming into contact with the silicon chip), a sound sensor (e.g., a microphone), an olfactory sensor (e.g., an “artificial nose”) and/or a sensor for measuring three dimensional biometric topology (e.g., a laser or ultrasound measuring device). The type of biometric sensor 71 used in an embodiment of the invention corresponds to the type of biometric information used by the methods of the invention.

[0089] The present invention may use any type of biometric information gathering and analysis as described herein or known to those skilled in the art. Biometric information includes information that when used alone or in combination with other information uniquely identifies an individual with reasonable certainty. Examples of biometric information include: retina metrics, iris metrics, voice print metrics, body measurement metrics, handwriting metric, body odor metrics, heart beat signature metrics and biometrics that may be discernable from the individual's body fluids such as blood, urine or breath. Retina metrics make use of individual blood vessel patterns on the retina of the eye which are photographed, encoded, and compared to a previously coded “enrollment.” Iris metrics similary refer to individualized patterns in the iris of the eye which are photographed, encoded, and compared to a previously coded “enrollment.” Voice print metrics capture a sample of an individual voice which reflect the physical structure producing the voice and the developmental speech patterns. Body measurement metrics map the physical measurement of the body and may include the physical characteristics of a finger, a hand, a face or other parts of the body. Handwriting metrics may include not only a comparison of the handwriting to a know sample, but also characteristics such as the speed, stroke order and pressure associated with, for instance, a signature. Use of physiological measurements as biometric information is discussed in more detail below.

[0090]FIG. 4 is a schematic block diagram illustrating the components of apparatus 26 in greater detail. Apparatus 26 includes a microprocessor 76, and a memory 80 connected to microprocessor 76. Memory 80 is preferably a non-volatile memory, such as a serial EEPROM. Memory 80 stores script programs 40 received from server 18, measurements 44 received from monitoring device 28, responses to queries, and a patient or patient type's unique identification code. . Unique information for identifying the individual may also be stored in the memory 80 of the apparatus 26, by the server 18, or both. This unique information may include a unique identification number or biometrics information about the individual that uniquely identifies that individual. Microprocessor 76 also includes built-in read only memory (ROM) which stores firmware for controlling the operation of apparatus 26. The firmware includes a script interpreter used by microprocessor 76 to execute script programs 40. The script interpreter interprets script commands which are executed by microprocessor 76.

[0091] The script commands allow apparatus 26 to identify the patient or patient type through user buttons 70A, 70B, 70C, and 70D, monitoring device 28, data card 65, or printer port 67. They also allow apparatus 26 to display the query sets to the patient, receive responses 42 to the query sets, receive measurements 44 from monitoring device 28, and transmit responses to server 18. Specific techniques for interpreting and executing script commands in this manner are well known in the art.

[0092] Microprocessor 76 is preferably connected to memory 80 using a standard two-wire I²C interface. Microprocessor 76 is also connected to user input buttons 70A, 70B, 70C, and 70D, data card reader 63, printer port 67, LED 74, a clock 84, and a display driver 82. Clock 84 indicates the current date and time to microprocessor 76. For clarity of illustration, clock 84 is shown as a separate component, but is preferably built into microprocessor 76. Display driver 82 operates under the control of microprocessor 76 to display information on display 64. Microprocessor 76 is preferably a PIC 16C65 processor which includes a universal asynchronous receiver transmitter (UART) 78. UART 78 is for communicating with a modem 86 and a device interface 90. A CMOS switch 88 under the control of microprocessor 76 alternately connects modem 86 and interface 90 to UART 78.

[0093] Modem 86 is connected to a telephone jack 22 through modem jack 66. Modem 86 is for exchanging data with server 18 through communication network 24. The data includes script programs 40 which are received from server 18 as well as responses 42 to queries, device measurements 44, script identification codes, and the patient or patient type's unique identification code or other information that uniquely identifies the individual which modem 86 transmits to server 18. Modem 86 is preferably a complete 28.8 K modem commercially available from Cermetek, although any suitable modem may be used.

[0094] Device interface 90 is connected to device jacks 68A, 68B, and 68C. Device interface 90 is for interfacing with a number of monitoring devices, such as blood glucose meters, respiratory flow meters, blood pressure cuffs, weight scales, or pulse rate monitors, through the device jacks. Device interface 90 operates under the control of microprocessor 76 to collect measurements 44 from the monitoring devices and to output the measurements to microprocessor 76 for storage in memory 80. In the preferred embodiment, device interface 90 is a standard RS232 interface. For simplicity of illustration, only one device interface is shown in FIG. 4. However, in alternative embodiments, apparatus 26 may include multiple device interfaces to accommodate monitoring devices 28 which have different connection standards.

[0095] The monitoring device 28 may include a biometric sensor 79 in lieu of or in addition to a biometric sensor 71 made part of the appratus 26. In addition to the types of biometric sensors 71 discussed above, a biometric sensor 79 may utilize or augment the data gathered by the monitoring device 28. For example, the biometric sensor 79 may make use of a heartbeat signature obtained by a pulse rate monitor, the blood characteristic obtained using a blood glucose meter, or the signature antigens present in a device reading a urine sample. Use of antigen signatures in urine to determine biometric information is the application Ser. No. ______, incorporated by reference.

[0096] Referring again to FIG. 2, server 18 includes a monitoring application 48. Monitoring application 48 is a controlling software application executed by server 18 to perform the various functions described below. Application 48 includes a script generator 50, a script assignor 52, and a report generator 54. Script generator 50 is designed to generate script programs 40 from script information entered through workstation 20. The script information is entered through a script entry screen 56. In the preferred embodiment, script entry screen 56 is implemented as a web page on server 18. Workstation 20 includes a web browser for accessing the web page to enter the script information.

[0097]FIG. 5 illustrates script entry screen 56 as it appears on workstation 20. Screen 56 includes a script name field 92 for specifying the name of script program 40 to be generated. Screen 56 also includes entry fields 94 for entering query sets to be answered by a patient. Each entry field 94 has corresponding response choice fields 96 for entering response choices for the query. Screen 56 further includes check boxes 98 for selecting desired monitoring device 28, such as a blood glucose meter, respiratory flow meter, or blood pressure cuff, from which to collect measurements 44.

[0098] Screen 56 additionally includes a connection time field 100 for specifying a prescribed connection time at which apparatus 26 executing the script is to establish a subsequent communication link to server 18. The connection time is preferably selected to be the time at which communication rates are the lowest, such as 3:00 AM. During this connection time, apparatus 26 transmits to server 18 all responses 42 and device measurements 44 it has received during the day. During this same connection time, apparatus 26 also receives from server 18 all script programs 40 it will need for the following day or until the next prescribed connection time. This store and forward feature of apparatus 26 reduces communication expenses. However, if numerous patients are using apparatus 26, more than one connection can be made during the day in order to download necessary script programs 40. Screen 56 also includes a CREATE SCRIPT button 102 for instructing script generator 50 to generate script program 40 from the information entered in screen 56. Screen 56 further includes a CANCEL button 104 for canceling the information entered in screen 56.

[0099] In the preferred embodiment, each script program 40 created by the script generator 50 conforms to the standard file format used on UNIX systems. In the standard file format, each command is listed in the upper case and followed by a colon. Every line in script program 40 is terminated by a linefeed character {LF}, and only one command is placed on each line. The last character in script program 40 is a UNIX end of file character {EOF}. Table 1 shows an exemplary listing of script commands used in the preferred embodiment of the invention. TABLE 1 SCRIPT COMMANDS Command Description CLS: {LF} Clear the display. ZAP: {LF} Erase from memory the last set of query responses recorded. LED: b{LF} Turn the LED on or off, where b is a binary digit of 0 or 1. An argument of 1 turns on the LED, and an argument of 0 turns off the LED. DISPLAY: {chars}{LF} Display the text following the DISPLAY command. INPUT: mmmm{LF} Record a button press. The m's represent a button mask pattern for each of the four input buttons. Each m contains an “X” for disallowed buttons or an “O” for allowed buttons. For example, INPUT: OXOX{LF} allows the user to press either button #1 or #3. WAIT: {LF} Wait for any one button to be pressed, then continue executing the script program. COLLECT: device{LF} Collect measurements from the monitoring device specified in the COLLECT command. The user is preferably prompted to connect the specified monitoring device to the apparatus and press a button to continue. NUMBER: aaaa{LF} Assign a script identification code to the script program. The script identification code from the most recently executed NUMBER state- ment is subsequently transmitted to the server along with the query responses and device measurements. The script identification code identifies to the server which script program was most recently executed by the remote apparatus. DELAY: t {LF} Wait until time t specified in the DELAY command, usually the prescribed connection time. CONNECT: {LF} Perform a connection routine to establish a communication link to the server, transmit the patient or patient type identification code, query responses, device measurements, and script identification code to the server, and receive and store a new script program. When the server instructs the apparatus to disconnect, the script interpreter is restarted, allowing the new script program to execute.

[0100] The script commands illustrated in Table 1 are representative of the preferred embodiment and are not intended to limit the scope of the invention. After consideration of the ensuing description, it will be apparent to one skilled in the art that many other suitable scripting languages and sets of script commands may be used to implement the invention.

[0101] Script generator 50 preferably stores a script program template which it uses to create each script program 40. To generate script program 40, script generator 50 inserts into the template the script information entered in screen 56. For example, FIGS. 6A-6B illustrate sample script program 40 created by script generator 50 from the script information shown in FIG. 5.

[0102] Script program 40 includes identification commands to determine the patient or patient type from user buttons 70A, 70B, 70C, and 70D, monitoring device 68A, 68B, and 68C, card chip reader 64, printer port 67, and display commands to display the queries and response choices entered in fields 94 and 96, respectively. Script program 40 also includes input commands to receive responses 42 to the queries. Script program 40 further includes a collect command to collect device measurements 44 from monitoring device 28 specified in check boxes 98. Script program 40 also includes commands to establish a subsequent communication link to server 18 at the connection time specified in field 100. The steps included in script program 40 are also shown in the flow chart of FIGS. 12A-12B and will be discussed in the operation section below.

[0103] Referring again to FIG. 2, script assignor 52 is for assigning script programs 40 to the patients. Script programs 40 are assigned in accordance with script assignment information entered through workstation 20. The script assignment information is entered through a script assignment screen 57, which is preferably implemented as a web page on server 18.

[0104]FIG. 7 illustrates a sample script assignment screen 57 as it appears on workstation 20. Screen 57 includes check boxes 106 for selecting script program 40 to be assigned and check boxes 108 for selecting the patient or patient types to whom script program 40 is to be assigned. Screen 57 also includes an ASSIGN SCRIPT button 112 for entering the assignments. When button 112 is pressed, script assignor 52 creates and stores for each patient or patient type selected in check boxes 108 a respective pointer to script program 40 selected in check boxes 106. Each pointer is stored in the patient or patient type look-up table 46 of database 38. Screen 57 further includes an ADD SCRIPT button 110 for accessing script entry screen 56 and a DELETE SCRIPT button 114 for deleting script program 40.

[0105] Referring again to FIG. 2, report generator 54 is designed to generate a patient report 58 from the responses and device measurements received in server 18. Patient report 58 is displayed on workstation 20. FIG. 10 shows a sample patient report 58 produced by report generator 54 for a selected patient. Patient report 58 includes a graph 116 of device measurements 44 received from the patient, as well as a listing of responses 42 received from the patient. Specific techniques for writing a report generator program to display data in this manner are well known in the art.

[0106] The operation of the preferred embodiment is illustrated in FIGS. 11A-C as. a flow chart illustrating steps included in the monitoring application executed by server 18. In step 202, server 18 determines if new script information has been entered through script entry screen 56. If new script information has not been entered, server 18 proceeds to step 206. If new script information has been entered, server 18 proceeds to step 204.

[0107] As shown in FIG. 5, the script information includes queries 94, and for each query 94, corresponding responses choices 96. The script information also includes a selected monitoring device type from which to collect device measurements 44. The script information further includes a prescribed connection time for each apparatus to establish a subsequent communication link to server 18. The script information is generally entered in server 18 by a healthcare provider, such as the patients' physician or case manager. Of course, any person desiring to communicate with the patients may also be granted access to server 18 to create and assign script programs 40. Further, it is to be understood that the system may include any number of workstations 20 for entering script generation and script assignment information in server 18.

[0108] In step 204, script generator 50 generates script program 40 from the information entered in screen 56. Script program 40 is stored in database 38. Steps 202 and 204 are preferably repeated to generate multiple script programs, e.g. a script program for diabetes patients, a script program for asthma patients, etc. Each script program 40 corresponds to a respective one of the sets of queries 94 entered through script entry screen 56. Following step 204, server 18 proceeds to step 206.

[0109] In step 206, server 18 determines if new script assignment information has been entered through assignment screen 57. If new script assignment information has not been entered, server 18 proceeds to step 210. If new script assignment information has been entered, server 18 proceeds to step 208. As shown in FIG. 7, script programs 40 are assigned to each patient by selecting script program 40 through check boxes 106, selecting the patient or patient types to whom selected script program 40 is to be assigned through check boxes 108, and pressing the ASSIGN SCRIPT button 112. When button 112 is pressed, script assignor 52 creates for each patient or patient type selected in check boxes 108 a respective pointer to script program 40 selected in check boxes 106. In step 208, each pointer is stored in look-up table 46 of database 38. Following step 208, server 18 proceeds to step 210.

[0110] In step 210, server 18 determines if apparatus 26 is remotely connected to server 18. If not, server 18 proceeds directly to step 220. If apparatus 26 is connected, server 18 determines in a decision step 211 whether to enforce security during communication with the remote apparatus 26. In an embodiment of the invention, biometrics are used to uniquely identify the individual using the remote apparatus 26. In a step 212 (FIG. 1B), biometric information is received from the remote appratus. The biometric information is compared to previously enrolled biometric information in a decision step 213 to determine if the biometric information sent by the remote apparatus 26 matches that of an authorized user. If the information does not match an authorized user, the communication is rejected in a step 221 and the method progresses to step 220.

[0111] If the biometric information does match an authorized user (step 213) or security is not enabled (step 211), the method continues with step 214 where the server 18 receives from apparatus 26 the patient or patient type's unique identification code. This step can be achieved in a number of ways. Biometric information identifying the patient can be sent at this point if not duplicative of biometric information previously sent (e.g., in step 212). The patient can answer specific queries on display 64 of apparatus 26, which allows identification of the patient's identity, condition, or disease. The patient's identification can also be recognized via monitoring device 28, including biometric information obtained by the monitoring device 28 or a biometric sensor 79 in communication with the monitoring device 28. Monitoring device 28 can contain the patient's unique identification code, and can send it to apparatus 26. Apparatus 26 is also capable of recognizing the type of monitoring device 28, for example a blood glucose meter, to determine the patient type, for example diabetes.

[0112] Data card reader 63 is a third way in which apparatus 26 can recognize a patient or patient type. Data card 65 contains information about the patient's identity, condition or disease, and possibly prescription information, which can be read by data card reader 63 of apparatus 26. This information is then sent to server 18, where it is used to determine which script program 40 is sent back to apparatus 26 to which the patient is to respond.

[0113] A fourth way in which apparatus 26 can identify a patient or patient type is through printer port 67, as illustrated in FIG. 20. Patient data from the server 106 of another information system can be sent to a printer 108 via apparatus 26. Apparatus 26 can then send the intercepted data to server 18 of the remote monitoring system of the present invention, which can then send appropriate script program 40 to apparatus 26. A more detailed description of the data interception embodiment of the present invention is described below.

[0114] In step 216, server 18 uses the patient identification code or individual identification information obtained as discussed above to retrieve from table 46 the pointer to script program 40 assigned to the patient. If the script program is to be customized for an indvidual, this is determined in a decision step 217 and custom information is merged into the script program in a step 218. The individual to customize the script program for is identified using the individual identification information. The customization of script programs is discussed below in more detail with reference to FIGS. 18-21. Server 18 then retrieves assigned script program 40 from database 38. In step 219, server 18 transmits assigned script program 40 to patient's apparatus 26 through communication network 24. Following step 218, server 18 proceeds to step 220.

[0115] In step 220, server 18 determines if a patient report request has been received from workstation 20. If no report request has been received, server 18 returns to step 202. If a report request has been received for a selected patient, server 18 retrieves from database 38, measurements 44 and query responses 42 last received from the patient, step 222. In step 224, server 18 generates and displays patient report 58 on workstation 20. As shown in FIG. 10, report 58 includes device measurements 44 and query responses 42 last received from the patient. Following step 224, the server returns to step 202.

[0116] FIGS. 12A-12B illustrate the steps executed by the remote apparatus 26. In a step 290, biometric information is gathered via a biometric sensor 71, 73 that is integrated with the remote apparatus 26 (FIGS. 3-4) or its various embodiments (e.g., FIGS. 15, 17). The remote sensor 79 may alternatively be integrated into a monitoring device 28 or may be a separate device that is placed into communication with the monitoring device 28 or the remote apparatus 26. Any biometric sensor that gathers information that gathers information that reasonably identifies an individual may be used. Since a number of biometric sensors are commercially available and known to those skilled in the art, they will only be briefly described herein. Examples of biometric sensors that may be used by the appratus 26 include an optical device (e.g., a camera created from a CCD), a silicon sensor (e.g., a chip that gathers information using the capacitance occurring as a result of a body part coming into contact with the silicon chip), a sound sensor (e.g., a microphone), an olfactory sensor (e.g., an “artificial nose”), a pressure sensor for detecting the speed, stroke order and pressure of handwriting and/or a sensor for measuring three dimensional biometric topology (e.g., a laser or ultrasound measuring device). The type of biometric sensor 71 used in an embodiment of the invention corresponds to the type of biometric information used by the methods of the invention.

[0117] Biometric information includes information that when used alone or in combination with other information uniquely identifies an individual with reasonable certainty. Examples of biometric information include: retina metrics, iris metrics, voice print metrics, body measurement metrics, handwriting metric, body odor metrics, heart beat signature metrics and biometrics that may be discernable from the individual's body fluids such as blood, urine or breath. Retina metrics make use of individual blood vessel patterns on the retina of the eye which are photographed, encoded, and compared to a previously coded “enrollment.” Iris metrics similary refer to individualized patterns in the iris of the eye which are photographed, encoded, and compared to a previously coded “enrollment.” Voice print metrics capture a sample of an individual voice which reflect the physical structure producing the voice and the developmental speech patterns. Body measurement metrics map the physical measurement of the body and may include the physical characteristics of a finger, a hand, a face or other parts of the body. Handwriting metrics may include not only a comparison of the handwriting to a know sample, but also characteristics such as the speed, stroke order and pressure associated with, for instance, a signature.

[0118] Referring to FIG. 12A, biometric information is gathered in a step 290. Security for the apparatus 26 may be configured separately from the security settings of the server 18. In a decision step 292, an apparatus configuration is checked to determine if security has been enabled for the remote apparatus 26. If security is not enabled, the method continues with step 296. If security is enabled, the biometric information collected in step 290 is checked in a decision step 294 against local biometric information maintained for authorized users. If the biometric information verifies with the local biometric information, the method continues with step 296. The method ends at step 334 (FIG. 12C) if the biometric information does not verify with the local biometric information.

[0119] The method continues with the script program 40 being executed by apparatus 26. Before script program 40 is received, apparatus 26 is programmed with the script interpreter used by microprocessor 76 to execute script program 40. The initial programming may be achieved during the connection to server 18. Following initial programming, apparatus 26 receives (step 296) from server 18 script program 40 assigned to the patient associated with apparatus 26. Script program 40 is received by modem 86 through a first communication link and stored in memory 80.

[0120] In step 302 (FIG. 12B), microprocessor 76 assigns a script identification code to script program 40 and stores the script identification code in memory 80. In step 304, microprocessor 76 lights LED 74 to notify the patient that he or she has unanswered queries stored in apparatus 26. LED 74 preferably remains lit until the queries are answered by the patient.

[0121] In step 308, microprocessor 76 prompts the patient by displaying on display 64 “ANSWER QUERIES NOW? PRESS ANY BUTTON TO START”. In step 310, microprocessor 76 waits until a reply to the prompt is received from the patient. When a reply is received, microprocessor 76 proceeds to step 312. In step 312, microprocessor 76 executes successive display and input commands to display the queries and response choices on display 64 and to receive responses 42 to the queries.

[0122]FIG. 8 illustrate a sample query and its corresponding response choices as they appear on display 64. The response choices are positioned on display 64 such that each response choice is located proximate to a respective one of input buttons 70A, 70B, 70C, and 70D. In the preferred embodiment, each response choice is displayed immediately above respective input button 70. The patient presses input button 70A, 70B, 70C, and 70D corresponding to his or her response. Microprocessor 76 stores each response in memory 80.

[0123] In steps 314-318, microprocessor 76 executes commands to collect device measurements 44 from selected monitoring device 28 if it is directed to do so by script program 40. Script program 40 specifies selected monitoring device 28 from which to collect measurements 44. In step 314, microprocessor 76 prompts the patient to connect selected monitoring device 28, for example a blood glucose meter, to one of device jacks 68A, 68B, and 68C. A sample prompt is shown in FIG. 10. In step 316, microprocessor 76 waits until a reply to the prompt is received from the patient. When a reply is received, microprocessor 76 proceeds to step 318. Microprocessor 76 also connects UART 78 to interface 90 through switch 88. In step 318, microprocessor 76 collects device measurements 44 from monitoring device 28 through interface 90. Measurements 44 are stored in memory 80.

[0124] In the preferred embodiment, apparatus 26 is always plugged into telephone jack 22. If not, however, microprocessor 76 prompts the patient to connect apparatus 26 to telephone jack 22 so that apparatus 26 may connect to server 18 at the prescribed connection time in step 320. In step 322, microprocessor 76 waits until a reply to the prompt is received from the patient. When a reply is received, microprocessor 76 turns off LED 74 in step 324. In step 326, microprocessor 76 waits until it is time to connect to server 18. Microprocessor 76 compares the connection time specified in script program 40 to the current time output by clock 84. When it is time to connect, microprocessor 76 connects UART 78 to modem 86 through switch 88.

[0125] In step 328, microprocessor 76 establishes a subsequent communication link between apparatus 26 and server 18 through modem 86 and communication network 24. If the connection fails for any reason, microprocessor 76 repeats step 328 to get a successful connection. Biometric information gathered by the remote apparatus 26 is transmitted to the server 18 in a step 329. In step 330, microprocessor 76 transmits device measurements 44, query responses 42, script identification code, and patient or patient type identification code stored in memory 80 to server 18 through the subsequent communication link. In step 332, microprocessor 76 receives through modem 86 new script program 40 from server 18. New script program 40 is stored in memory 80 for subsequent execution by microprocessor 76. Following step 332, script program 40 ends.

[0126] In the above description, apparatus 26 connects to server 18 each time a new patient identification is entered. FIG. 13 shows an alternative embodiment, where apparatus 26 connects to server 18 at one time during the day. During this connection period, apparatus 26 receives from server 18 all script programs 40 it expects to need during the following day. As shown in FIG. 13, steps 202-208 are the same as above, with server 18 generating and storing new script assignments and new script programs if needed. In step 210, apparatus 26 connects with server 18. In step 216, server 18 retrieves script programs 40 from database 38. Script programs 40 can be for patients who are likely to use apparatus 26 the following day, or script programs 40 can be for general conditions, diseases, or prescriptions that are requested everyday. In step 218, server 18 transmits assigned script program 40 to patient's apparatus 26 through communication network 24. Following step 218, server 18 proceeds to step 220, which is carried out in the same manner as the embodiment illustrated in FIGS. 11A and 11B.

[0127] In the embodiment of FIG. 13, patients' responses to all queries are transmitted from apparatus 26 to server 18 during a single connection period, ideally the same connection period when script programs 40 are downloaded into apparatus 26 for the following day. FIGS. 14A and 14B show the steps of script program 40 for the embodiment of FIG. 13. Notice all steps are the same, except for the addition of step 325. In step 325, apparatus 26 has the option of repeating another script program sequence for the same or another patient before connecting to server 18. Thus, many patients can use apparatus 26 during the day. Apparatus 26 stores all their responses 42 and measurements 44, and then forwards them to server 18 at the end of the day, as shown in step 330. Apparatus 26 used in this embodiment must have sufficient memory means 80.

[0128] The main advantage of the present invention is that it does not require that each patient purchase his or her own apparatus 26. Instead, patients can visit their nearest pharmacy or healthcare clinic where apparatus 26 is located and answer queries there. Since apparatus 26 only requires identification of a patient or patient type in order to connect to server 18 and download appropriate script program 40, any patient can use any apparatus 18 as long as they have a patient identification code, data card, or monitoring device. Ideally, patients who are traveling or are far from home can just stop into any pharmacy and answer queries, which will get sent back to server 18.

[0129] A second advantage of the monitoring system is that it allows each apparatus 26 to be programmed remotely through script programs 40. Patient surveys, connection times, display prompts, selected monitoring devices, patient customization, and other operational details of each apparatus may be easily changed by transmitting a new script program 40 to apparatus 26. Moreover, each script program 40 may be easily created and assigned by remotely accessing server through 18 the Internet. Thus, the invention provides a powerful, convenient, and inexpensive system for remotely monitoring a large number of patients.

[0130] FIGS. 16-18 illustrate a second embodiment of the invention in which each remotely programmable apparatus has speech recognition and speech synthesis functionality. FIG. 14 shows a perspective view of an apparatus 27 according to the second embodiment. Apparatus 27 includes a speaker 72 for audibly communicating queries and prompts to the patient. Apparatus 27 also includes a microphone 118 for receiving spoken responses to the queries and prompts. Apparatus 27 may optionally include a display 64 for displaying prompts to the patient, as shown in FIG. 17.

[0131]FIG. 18 is a schematic block diagram illustrating the components of apparatus 27 in greater detail. Apparatus 27 is similar in design to apparatus 26 of the preferred embodiment except that apparatus 27 includes an audio processor chip 120 in place of microprocessor 76. Audio processor chip 120 is preferably an RSC-164 chip commercially available from Sensory Circuits Inc. of 1735 N. First Street, San Jose, Calif. 95112.

[0132] Audio processor chip 120 has a microcontroller 122 for executing script programs 40 received from server 18. A memory 80 is connected to microcontroller 122. Memory 80 stores script programs 40 and a script interpreter used by microcontroller 122 to execute script programs 40. Memory 80 also stores measurements 44 received from monitoring device 28, responses 42 to the queries, and script identification codes.

[0133] Audio processor chip 120 also has built in speech synthesis functionality for synthesizing queries and prompts to a patient through speaker 72. For speech synthesis, chip 120 includes a digital to analog converter (DAC) 142 and an amplifier 144. DAC 142 and amplifier 144 drive speaker 72 under the control of microcontroller 122.

[0134] Audio processor chip 120 further has built in speech recognition functionality for recognizing responses spoken into microphone 118. Audio signals received through microphone 118 are converted to electrical signals and sent to a preamp and gain control circuit 128. Preamp and gain control circuit 128 is controlled by an automatic gain control circuit 136, which is in turn controlled by microcontroller 122. After being amplified by preamp 128, the electrical signals enter chip 120 and pass through a multiplexer 130 and an analog to digital converter (ADC) 132. The resulting digital signals pass through a digital logic circuit 134 and enter microcontroller 122 for speech recognition.

[0135] Audio processor chip 120 also includes a RAM 138 for short term memory storage and a ROM 140 which stores programs executed by microcontroller 122 to perform speech recognition and speech synthesis. Chip 120 operates at a clock speed determined by a crystal 126. Chip 120 also includes a clock 84 which provides the current date and time to microcontroller 122. As in the preferred embodiment, apparatus 27 includes an LED 74, display driver 82, modem 86, and device interface 90, all of which are connected to microcontroller 122.

[0136] The operation of the second embodiment is similar to the operation of the preferred embodiment except that queries, response choices, and prompts are audibly communicated to the patient through speaker 72 rather than being displayed to the patient on display 64. The operation of the second embodiment also differs from the operation of the preferred embodiment in that responses 42 to the queries and prompts are received through microphone 118 rather than through user input buttons.

[0137] Script programs 40 of the second embodiment are similar to the script program shown in FIGS. 6A-6B, except that each display command is replaced by a speech synthesis command and each input command is replaced by a speech recognition command. The speech synthesis commands are executed by microcontroller 122 to synthesize queries, response choices, and prompts through speaker 72. The speech recognition commands are executed by microcontroller 122 to recognize responses 42 spoken into microphone 118.

[0138] For example, to ask the patient how he or she feels and record a response, microcontroller 122 first executes a speech synthesis command to synthesize through speaker 72 “How do you feel? Please answer with one of the following responses: very bad, bad, good, or very good.” Next, microcontroller 118 executes a speech recognition command to recognize the response spoken into microphone 118. The recognized response is stored in memory 80 and subsequently transmitted to server 18. Other than the differences described, the operation and advantages of the second embodiment are the same as the operation and advantages of the preferred embodiment described above.

[0139] Although the first and second embodiments focus on querying individuals and collecting responses to the queries, the system of the invention is not limited to querying applications. The system may also be used simply to communicate messages to the individuals. FIGS. 18-21 illustrate a third embodiment in which the system is used to perform this automated messaging function. In the third embodiment, each script program contains a set of statements to be communicated to an individual rather than a set of queries to be answered by the individual. Of course, it will be apparent to one skilled in the art that the script programs may optionally include both queries and statements.

[0140] The third embodiment also shows how the queries and statements may be customized to each individual by merging personal data with the script programs, much like a standard mail merge application. Referring to FIG. 18, personal data relating to each individual is preferably stored in look-up table 46 of database 38. By way of example, the data may include each individual's name, the name of each individual's physician, test results, appointment dates, or any other desired data. As in the preferred embodiment, database 38 also stores generic script programs 40 created by script generator 50.

[0141] Server 18 includes a data merge program 55 for merging the data stored in table 46 with generic script programs 40. Data merge program 55 is designed to retrieve selected data from table 46 and to insert the data into statements in generic script programs 40, thus creating custom script programs 41. Each custom script program 41 contains statements which are customized to an individual. For example, the statements may be customized with the individual's name, test results, etc. Examples of such customized statements are shown in FIGS. 19 and 20.

[0142] The operation of the third embodiment is similar to the operation of the preferred embodiment except that script programs 40 are used to communicate messages to the individuals rather than to query the individuals. Each message is preferably a set of statements. Referring to FIG. 18, the statements may be entered in server 18 through script entry screen 56, just like the queries of the preferred embodiment.

[0143] Each statement preferably includes one or more insert commands specifying data from table 46 to be inserted into the statement. The insert commands instruct data merge program 55 to retrieve the specified data from database 38 and to insert the data into the statement. For example, the insert commands shown in FIG. 21 instruct the data merge program to insert a physician name, an appointment date, a patient name, and a test result into the statements. As in the preferred embodiment, each statement may also include one or more response choices which are entered in fields 96.

[0144] Following entry of the statements and response choices, CREATE SCRIPT button 102 is pressed. When button 102 is pressed, script generator 50 generates a generic script program from the information entered in screen 56. The generic script program is similar to script program 40 shown in FIGS. 6A-6B, except that the display commands specify statements to be displayed rather than queries. Further, the statements include insert commands specifying data to be inserted into script program 40. As in the preferred embodiment, multiple script programs are preferably generated, e.g. a generic script program for diabetes patients, a generic script program for asthma patients, etc. The generic script programs are stored in database 38.

[0145] Following generation of the generic script programs, server 18 receives script assignment information entered through script assignment screen 57. As shown in FIG. 7, script programs 40 are assigned by first selecting one of the generic script programs through check boxes 106, selecting individuals through check boxes 108, and pressing the ASSIGN SCRIPT button 112. When button 112 is pressed, data merge program 55 creates a custom script program for each individual selected in check boxes 108.

[0146] Each custom script program is preferably created by using the selected generic script program as a template. For each individual selected, data merge program 55 retrieves from database 38 the data specified in the insert commands. Next, data merge program 55 inserts the data into the appropriate statements in the generic script program to create a custom script program for the individual. Each custom script program is stored in database 38.

[0147] As each custom script program is generated for an individual, script assignor 52 assigns the custom script program to the individual. This is preferably accomplished by creating a pointer to the custom script program and storing the pointer with the individual's unique identification code in table 46. When the individual's remote apparatus connects to server 18, server 18 receives from apparatus 26 the individual's unique identification code. Server 18 uses the unique identification code to retrieve from table 46 the pointer to the custom script program assigned to the individual. Next, server 18 retrieves the assigned custom script program from database 38 and transmits the assigned custom script program to apparatus 26 through communication network 24.

[0148] Apparatus 26 receives and executes script program 40. The execution of script program 40 is similar to the execution described in the preferred embodiment, except that statements are displayed to the individual rather than queries. FIGS. 17-18 illustrate two sample statements as they appear on display 64. Each statement includes a response choice, preferably an acknowledgment such as “OK”. After reading a statement, the individual presses the button corresponding to the response choice to proceed to the next statement. Alternatively, script program 40 may specify a period of time that each statement is to be displayed before proceeding to the next statement. The remaining operation of the third embodiment is analogous to the operation of the preferred embodiment described above.

[0149] The multi-user capabilities of the present invention allow for the collection and tracking of patient data. Apparatuses 26 are connected to one or more servers 18. They are placed in a number of different public places, such as pharmacies, where they are accessible to a wide range of patients. Patient responses 42 and measurements 44 are received by apparatuses 26 in the manner described above. The data is then sent to server or servers 18 where it is collected and organized. Ideally, pharmaceutical companies or healthcare providers will use monitoring system 16 to gather patient response to their products or services. The companies or providers will send queries or script programs 40 to server 18, which will then send queries or script programs 40 to one or more apparatuses 26. After patients have answered the queries or attached their monitoring devices 28, server 18 will send the patient data back to the companies and providers.

[0150]FIG. 22 shows how the present invention can be used in conjunction with a separate information system, such as a pharmacy information system. Patient data from the pharmacy information system 105 can be intercepted by the apparatus 29 in order to trigger the execution of script programs 40. In this embodiment, apparatus 29 is located in series between the pharmacy server 106 of pharmacy information system 105 and the pharmacy printer 108. Pharmacy information system 105 comprises pharmacy server 106, pharmacy workstation 107, and pharmacy printer 108. Patient data sent from pharmacy server 106 to pharmacy printer 108 must pass through apparatus 29. Apparatus 29 takes the patient data and sends it to server 18 of the system of the present invention. Server 18 uses patient data to determine which script program 40 to send to apparatus 29 for patient to answer. It is obvious that this method can be used to identify the patient to apparatus 29 and also server 18.

[0151] Alternatively, interception of patient data by apparatus 29 can be used to trigger printing of information on pharmacy printer 108. In this embodiment, apparatus 29 is again located in series between pharmacy server 106 of separate information system 105 and pharmacy printer 108. When apparatus 29 receives the patient data, it triggers a stored script program 40, which commands pharmacy printer 108 to print out information for the patient. This information differs in content from the patient data and is printed in addition to it. In addition, the patient data can also be sent to server 18 to trigger additional script program 40 which displays queries on display 64 of apparatus 29 to be answered by patient.

[0152]FIG. 23 shows a block diagram of apparatus 29 as used in this emnbodiment, while FIG. 24 shows a schematic block diagram illustrating the components of apparatus 29 in greater detail. FIGS. 23 and 24 are similar to FIGS. 3 and 4, except for the addition of a server port 69 in both figures. Server port 69 is used to connect apparatus 29 to pharmacy server 106. Server port 69 can receive a standard SCSI cable connection or a telephone cable connection, in which case it operates as a modem. Thus apparatus 29 can connect to server 18 through modem jack 66, pharmacy server 106 through server port 69, monitoring device 28 through device jacks 68A, 68B, and 68C, and pharmacy printer 108 through printer port 67.

SUMMARY, RAMIFICATIONS, AND SCOPE

[0153] Although the above description contains many specificities, these should not be construed as limitations on the scope of the invention but merely as illustrations of some of the presently preferred embodiments. Many other embodiments of the invention are possible. For example, the scripting language and script commands shown are representative of the preferred embodiment. It will be apparent to one skilled in the art many other scripting languages and specific script commands may be used to implement the invention.

[0154] Moreover, the invention is not limited to the specific applications described. The system and method of the invention have many other applications both inside and outside the healthcare industry. For example, the system may also be used by insurance companies and medical clinics to conduct all types of surveys of patients. Retailers and service companies can conduct all types of surveys of consumers. Marketing firms can use the invention to do widespread market research. In addition, stores can use the invention to receive information from customers regarding their shopping tastes. An example of this application would be a bridal registry.

[0155] The invention may also be used for educational purposes, such as testing students remotely. Students can use the apparatus to take national standardized multiple-choice tests, such as the Graduate Record Examination (GRE). In addition, the invention can be used for financial purposes. Banks, utilities, credit card companies, etc. can send billing information from their servers to customers using the apparatuses. Customers can then authorize the institutions to transfer funds, pay their bills, etc.

[0156] Therefore, the scope of the invention should be determined not by the examples given, but by the appended claims and their legal equivalents. 

What is claimed is:
 1. A method for remotely administering a person's health care, comprising: providing a remote apparatus having a user interface to the person; providing a server system having a script generator for generating script programs; collecting biometric information pertaining to the person via the remote apparatus; sending the biometric information pertaining to the person from the remote apparatus to the server system via a communication network; generating the script program with the script generator at the server system based in part on the biometric information; and sending the script program to the remote apparatus via the communication network for interaction with the person.
 2. The method of claim 1, wherein the remote apparatus verifies the biometric information as that of an authorized user before the remote apparatus can be used.
 3. The method of claim 1, wherein the server computer provides security based on the biometric information.
 4. The method of claim 3, wherein the server computer limits access to an individualized script program based on the biometric information.
 5. The method of claim 1, wherein the biometric information is collected via the user interface of the remote apparatus.
 6. The method of claim 5, wherein the script generator individualizes the script program to the person using the biometric information.
 7. The method of claim 5, wherein the biometric information comprises information that uniquely identifies the person.
 8. The method of claim 7, wherein the script generator individualizes the script program to the person using the biometric information.
 9. The method of claim 7, wherein the biometric information comprises retinal metrics.
 10. The method of claim 7, wherein the biometric information comprises iris metrics.
 11. The method of claim 7, wherein the biometric information comprises body measurement metrics.
 12. The method of claim 7, wherein the biometric information comprises body odor metrics.
 13. The method of claim 7, wherein the biometric information comprises voice print metrics.
 14. The method of claim 1, wherein the biometric information is collected via a monitoring device connected to the remote apparatus.
 15. The method of claim 14, wherein the script generator individualizes the script program to the person using the biometric information.
 16. The method of claim 14, wherein the biometric information comprises information that uniquely identifies the person.
 17. The method of claim 16, wherein the remote apparatus verifies the biometric information as that of an authorized user before the remote apparatus can be used.
 18. The method of claim 16, wherein the server computer provides security based on the biometric information.
 19. The method of claim 18, wherein the server computer limits access to an individualized script program based on the biometric information.
 20. The method of claim 14, wherein the script generator individualizes the script program to the person using the biometric information.
 21. The method of claim 14, wherein the biometric information comprises a heart beat signature.
 22. The method of claim 14, wherein the biometric information comprises a physiological measurement.
 23. The method of claim 22, wherein the physiological measurement includes information pertaining to a body fluid.
 24. The method of claim 23, wherein the body fluid is breath.
 25. The method of claim 23, wherein the body fluid is blood.
 26. The method of claim 23, wherein the body fluid is urine.
 27. The method of claim 26, wherein the biometric information is determined for the urine using an antigen signature of the urine.
 28. A system for the management of a person's health care, comprising: a remote apparatus having a user interface for interaction with the person; a server system having script programs pertaining the person's health care; a communication network linking the remote apparatus and server system for communication of the script program to the remote apparatus; a biometric sensor for collecting biometric information from the person.
 29. The system of claim 28, wherein the remote apparatus includes the biometric sensor.
 30. The system of claim 28, wherein a monitoring device connected to the remote apparatus includes the biometric sensor.
 31. The system of claim 28, wherein the server system includes a script generator for generating an individual script program based at least in part on the biometric information.
 32. The system of claim 28, wherein the remote apparatus uses the biometric information to authorize the person using the remote apparatus.
 33. The system of claim 28, wherein the server system uses the biometric information to authorize the server system to communicate with the remote apparatus.
 34. The method of claim 28, wherein the biometric information comprises information that uniquely identifies the person.
 35. The method of claim 34, wherein the biometric information comprises retinal metrics.
 36. The method of claim 34, wherein the biometric information comprises iris metrics.
 37. The method of claim 34, wherein the biometric information comprises body measurement metrics.
 38. The method of claim 34, wherein the biometric information comprises body odor metrics.
 39. The method of claim 34, wherein the biometric information comprises voice metrics.
 40. The method of claim 34, wherein the biometric information comprises a heart beat signature.
 41. The method of claim 34, wherein the biometric information comprises a physiological measurement.
 42. The method of claim 41, wherein the physiological measurement includes information pertaining to a body fluid.
 43. The method of claim 42, wherein the body fluid is breath.
 44. The method of claim 42, wherein the body fluid is blood.
 45. The method of claim 42, wherein the body fluid is urine.
 46. The method of claim 45, wherein the biometric information is determined for the urine using an antigen signature of the urine. 